Features Introduced in the 9.8.1 Windows Release

This section provides details about the new features introduced in the Windows 9.8.1 release.

Secured RMS License Manager Communication

An industry-standard secret-key authenticated encryption is now being used for securing the RMS License Manager communication with the various components. Prior to this release, a proprietary encryption algorithm was being used for securing the RMS License Manager communication. This impacts the exchange of communication messages:

>Between client application and RMS License Manager

>Between RMS License Managers in the redundant pool

>Between SCP service and RMS License Manager

For more information, refer to RMS License Manager Communication.

Sentinel RMS 9.8.1 Release Notes

>Windows

>Linux

>Mac

>Android

>Linux ARM

Introduced a Library to Maintain Support of Proprietary Encryption Algorithm

If under certain scenarios, you still want to use proprietary encryption algorithm, you need to deploy a separate compatibility-mode library with the v9.8.1 (or later) licensing libraries. To obtain this library, you need to contact Technical Support.

Updates in the RMS License Manager Configuration Options

In this release, a new command-line option -enable-localhost-check is added. This option applies restrictions to perform the following operations on the RMS License Manager from other machines in a network:

>Addition/installation of licenses

>Deletion/uninstallation of licenses

>Shutting down of RMS License Manager

For more information, refer to Sentinel RMS System Administrator Guide.

Modified License Loading Behavior on RMS License Manager Restart

With the new encryption algorithm in place, now when the v9.8.1 (or later) RMS License Manager is restarted, additional tasks related to key-exchange are performed by the running licensed application. During this interval, the licensed application attempting to contact the License Manager (such as for automatic renewal calls via auto timer), may return with error 210133 (SNTL_RESOURCE_LOCK_FAILURE). To overcome this, try calling the licensing API again after few seconds.